IP SLA (Internet protocol service level agreement) is a feature of the Cisco Internetwork Operating System (Cisco IOS) that allows an IT professional to collect information about network performance in real time. Cisco IOS IP SLAs continuously collect data about such things as response times, latency, jitter and packet loss. This not only provides the network administrator with baseline information about network performance. IP SLAs are especially useful for wide area networks (WANs) that connect multiple geographies and needs to be monitored from one central location.
Requirement:
- Configure IP addresses as per topology
- Configure EIGRP among ISP1 routers and between ISP1 and ISP2
- Configure Default and static routes as per need between customers and ISPs
- Configure SLA for icmp echo between customer 3 and customer 1.
- Configure SLA for path-echo between customer1 and customer2
verify results by using following commands - debug ip sla trace
- show ip sla statistics
- debug ip sla err
| ! Customer1 Configuration interface Loopback0 ip address 150.1.1.1 255.255.255.255 interface Serial0/0 ip address 10.1.1.129 255.255.255.252 no shut ip route 0.0.0.0 0.0.0.0 10.1.1.130 ip sla responder ip sla 10 path-echo 10.1.1.194 verify-data frequency 10 ip sla schedule 10 life 40 start-time now ! Cutomer2 Configuration interface Loopback0 ip address 15.1.1.1 255.255.255.255 interface Serial0/0 ip address 10.1.1.194 255.255.255.252 no shut ip route 0.0.0.0 0.0.0.0 10.1.1.193 ip sla responder ! Customer3 Configuration interface Loopback0 ip address 90.1.1.1 255.255.255.255 interface Serial0/0 ip address 11.1.1.194 255.255.255.252 no shut ip route 0.0.0.0 0.0.0.0 11.1.1.193 ip sla 1 icmp-echo 150.1.1.1 verify-data frequency 5 ip sla schedule 1 life 60 start-time now ! ISPR1 Configuration interface FastEthernet0/0 ip address 10.1.1.1 255.255.255.252 no shut interface Serial0/0 ip address 10.1.1.130 255.255.255.252 no shut router eigrp 10 redistribute static network 10.0.0.0 no auto-summary ip route 150.1.1.1 255.255.255.255 10.1.1.129 ! ISP2R2 Configuration interface FastEthernet0/0 ip address 10.1.1.2 255.255.255.252 no shut interface Serial0/0 ip address 10.1.1.193 255.255.255.252 no shut interface Serial0/1 ip address 11.1.1.1 255.255.255.252 no shut router eigrp 10 redistribute static network 10.0.0.0 network 11.0.0.0 no auto-summary ip route 15.1.1.1 255.255.255.255 10.1.1.194 ! ISP2R1 Configuration interface Serial0/0 ip address 11.1.1.2 255.255.255.252 no shut interface Serial0/1 ip address 11.1.1.193 255.255.255.252 no shut router eigrp 10 redistribute static network 11.0.0.0 no auto-summary ip route 90.1.1.1 255.255.255.255 11.1.1.194 | Configuration Explanation Providing ip address to loopback 0 Providing IP address to serial 0/0 Default Route The Cisco IOS IP SLAs Responder is a component embedded in the destination Cisco routing device that allows the system to anticipate and respond to Cisco IOS IP SLAs request packets. The Cisco IOS IP SLAs Responder provides an enormous advantage with accurate measurements without the need for dedicated probes Enabling IP SLA. Number is the identification of this SLA and it is locally important. The IP SLAs ICMP Path Echo operation records statistics for each hop along the path that the IP SLAs operation takes to reach its destination. (Optional) Causes an IP SLAs operation to check each reply packet for data corruption. (Optional) Set the rate at which a specified IP SLAs operation repeats. Configures the scheduling parameters for a single IP SLAs operation. use the ip sla schedule command in global configuration mode |
Verification by Debugging
Customer3(config)#
*Mar 1 02:17:29.311: IP SLAs(1) Scheduler: Starting an operation
*Mar 1 02:17:29.311: IP SLAs(1) echo operation: Sending an echo operation -
destAddr=150.1.1.1, sAddr=11.1.1.194
*Mar 1 02:17:29.311: IP SLAs(1) echo operation: Sending ID: 7
*Mar 1 02:17:29.527: IP SLAs(1) echo operation: RTT=212
*Mar 1 02:17:29.527: IP SLAs(1) Scheduler: Updating result
*Mar 1 02:17:29.531: IP SLAs(1) Scheduler: life left 59784
*Mar 1 02:17:29.531: IP SLAs(1) Scheduler: is it random? 0
*Mar 1 02:17:29.531: IP SLAs(1) Scheduler: start wakeup timer, delay = 4780
*Mar 1 02:17:34.311: IP SLAs(1) Scheduler: saaSchedulerEventWakeup
*Mar 1 02:17:34.311: IP SLAs(1) Scheduler: Starting an operation
*Mar 1 02:17:34.311: IP SLAs(1) echo operation: Sending an echo operation -
destAddr=150.1.1.1, sAddr=11.1.1.194
*Mar 1 02:17:34.315: IP SLAs(1) echo operation: Sending ID: 7
*Mar 1 02:17:34.427: IP SLAs(1) echo operation: RTT=112
*Mar 1 02:17:34.427: IP SLAs(1) Scheduler: Updating result
*Mar 1 02:17:34.427: IP SLAs(1) Scheduler: life left 54884
*Mar 1 02:17:34.431: IP SLAs(1) Scheduler: is it random? 0
*Mar 1 02:17:34.431: IP SLAs(1) Scheduler: start wakeup timer, delay = 4880
Customer1(config)#
*Mar 1 02:33:24.391: IP SLAs(10) Scheduler: Starting an operation
*Mar 1 02:33:24.395: IP SLAs(10) pathEcho operation: Sending a pathEcho operation
*Mar 1 02:33:24.399: IP SLAs(10) pathEcho operation: Sending Packet to 10.1.1.194 with ttl = 1
*Mar 1 02:33:24.407: IP SLAs(10) pathEcho operation: Return Value of ! for target 10.1.1.130
*Mar 1 02:33:24.407: IP SLAs(10) pathEcho operation: Adding hop - 10.1.1.130
*Mar 1 02:33:24.407: IP SLAs(10) pathEcho operation: Sending Packet to 10.1.1.194 with ttl = 2
*Mar 1 02:33:24.619: IP SLAs(10) pathEcho operation: Return Value of ! for target 10.1.1.2
*Mar 1 02:33:24.623: IP SLAs(10) pathEcho operation: Adding hop - 10.1.1.2
*Mar 1 02:33:24.623: IP SLAs(10) pathEcho operation: Sending Packet to 10.1.1.194 with ttl = 3
*Mar 1 02:33:24.823: IP SLAs(10) pathEcho operation: Return Value of U for target 10.1.1.194
*Mar 1 02:33:24.823: IP SLAs(10) pathEcho operation: Adding hop - 10.1.1.194
*Mar 1 02:33:24.951: IP SLAs(10) pathEcho operation: Hop 10.1.1.130 Response Time 124
*Mar 1 02:33:25.103: IP SLAs(10) pathEcho operation: Hop 10.1.1.2 Response Time 152
*Mar 1 02:33:25.255: IP SLAs(10) pathEcho operation: Hop 10.1.1.194 Response Time 149
*Mar 1 02:33:25.255: IP SLAs(10) Scheduler: Updating result
*Mar 1 02:33:25.263: IP SLAs(10) Scheduler: life left 39128
*Mar 1 02:33:25.263: IP SLAs(10) Scheduler: is it random? 0
*Mar 1 02:33:25.263: IP SLAs(10) Scheduler: start wakeup timer, delay = 9128
Customer1(config)#
*Mar 1 02:17:29.311: IP SLAs(1) Scheduler: Starting an operation
*Mar 1 02:17:29.311: IP SLAs(1) echo operation: Sending an echo operation -
destAddr=150.1.1.1, sAddr=11.1.1.194
*Mar 1 02:17:29.311: IP SLAs(1) echo operation: Sending ID: 7
*Mar 1 02:17:29.527: IP SLAs(1) echo operation: RTT=212
*Mar 1 02:17:29.527: IP SLAs(1) Scheduler: Updating result
*Mar 1 02:17:29.531: IP SLAs(1) Scheduler: life left 59784
*Mar 1 02:17:29.531: IP SLAs(1) Scheduler: is it random? 0
*Mar 1 02:17:29.531: IP SLAs(1) Scheduler: start wakeup timer, delay = 4780
*Mar 1 02:17:34.311: IP SLAs(1) Scheduler: saaSchedulerEventWakeup
*Mar 1 02:17:34.311: IP SLAs(1) Scheduler: Starting an operation
*Mar 1 02:17:34.311: IP SLAs(1) echo operation: Sending an echo operation -
destAddr=150.1.1.1, sAddr=11.1.1.194
*Mar 1 02:17:34.315: IP SLAs(1) echo operation: Sending ID: 7
*Mar 1 02:17:34.427: IP SLAs(1) echo operation: RTT=112
*Mar 1 02:17:34.427: IP SLAs(1) Scheduler: Updating result
*Mar 1 02:17:34.427: IP SLAs(1) Scheduler: life left 54884
*Mar 1 02:17:34.431: IP SLAs(1) Scheduler: is it random? 0
*Mar 1 02:17:34.431: IP SLAs(1) Scheduler: start wakeup timer, delay = 4880
Customer1(config)#
*Mar 1 02:33:24.391: IP SLAs(10) Scheduler: Starting an operation
*Mar 1 02:33:24.395: IP SLAs(10) pathEcho operation: Sending a pathEcho operation
*Mar 1 02:33:24.399: IP SLAs(10) pathEcho operation: Sending Packet to 10.1.1.194 with ttl = 1
*Mar 1 02:33:24.407: IP SLAs(10) pathEcho operation: Return Value of ! for target 10.1.1.130
*Mar 1 02:33:24.407: IP SLAs(10) pathEcho operation: Adding hop - 10.1.1.130
*Mar 1 02:33:24.407: IP SLAs(10) pathEcho operation: Sending Packet to 10.1.1.194 with ttl = 2
*Mar 1 02:33:24.619: IP SLAs(10) pathEcho operation: Return Value of ! for target 10.1.1.2
*Mar 1 02:33:24.623: IP SLAs(10) pathEcho operation: Adding hop - 10.1.1.2
*Mar 1 02:33:24.623: IP SLAs(10) pathEcho operation: Sending Packet to 10.1.1.194 with ttl = 3
*Mar 1 02:33:24.823: IP SLAs(10) pathEcho operation: Return Value of U for target 10.1.1.194
*Mar 1 02:33:24.823: IP SLAs(10) pathEcho operation: Adding hop - 10.1.1.194
*Mar 1 02:33:24.951: IP SLAs(10) pathEcho operation: Hop 10.1.1.130 Response Time 124
*Mar 1 02:33:25.103: IP SLAs(10) pathEcho operation: Hop 10.1.1.2 Response Time 152
*Mar 1 02:33:25.255: IP SLAs(10) pathEcho operation: Hop 10.1.1.194 Response Time 149
*Mar 1 02:33:25.255: IP SLAs(10) Scheduler: Updating result
*Mar 1 02:33:25.263: IP SLAs(10) Scheduler: life left 39128
*Mar 1 02:33:25.263: IP SLAs(10) Scheduler: is it random? 0
*Mar 1 02:33:25.263: IP SLAs(10) Scheduler: start wakeup timer, delay = 9128
Customer1(config)#
RSS Feed